Slice allocation

ABSTRACT

Certain aspects of the present disclosure provide techniques for communicating, by a user equipment (UE), over multiple slices. A method that may be performed by the UE includes receiving, by a modem, from an operating system (OS), a request for route identifier, the request for route identifier comprising a traffic descriptor corresponding to a first application from which the request for route identifier originated. The method further includes transmitting a route identifier to the OS, the route identifier generated by the modem based on a routing policy that provides mapping between the traffic descriptor and a network route. The method further includes receiving, by the modem, a start network request comprising the route identifier. The method further includes establishing, in response to the start network request, a network connection via the network route.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims divisional application of U.S. Non Provisionalpatent application Ser. No. 17/172,492, filed Feb. 10, 2021, whichclaims benefit of and priority to U.S. Provisional Application No.62/976,258, filed Feb. 13, 2020, which is hereby expressly incorporatedby reference herein in its entirety as if fully set forth below and forall applicable purposes.

BACKGROUND Field of the Disclosure

Aspects of the present disclosure relate to wireless communications, andmore particularly, to techniques for providing wireless communicationusing multiple slices on a single user equipment (UE).

Description of Related Art

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,broadcasts, etc. These wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, etc.). Examples of such multiple-access systems include3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)systems, LTE Advanced (LTE-A) systems, code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems, to name a few.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. New radio (e.g., 5G NR) is an exampleof an emerging telecommunication standard. NR is a set of enhancementsto the LTE mobile standard promulgated by 3GPP. NR is designed to bettersupport mobile broadband Internet access by improving spectralefficiency, lowering costs, improving services, making use of newspectrum, and better integrating with other open standards using OFDMAwith a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL).To these ends, NR supports beamforming, multiple-input multiple-output(MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in NR and LTEtechnology. Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedwireless communication.

Certain aspects are directed to a method for wireless communication at auser equipment (UE). In some examples, the method includes transmitting,from an operating system (OS) to a modem, an indication of a startnetwork request originating from an application, the transmitting of theindication based on a determination that a traffic descriptor associatedwith the application is a non-default descriptor. In some examples, themethod includes determining one or more parameters for establishing anew network connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters. In some examples, themethod includes transmitting, to the application, an indication that thenew network connection has been established based on the one or moreparameters.

Certain aspects are directed to an apparatus for wireless communication.In some examples, the UE includes a memory and a processor coupled tothe memory. In some examples, the memory and the processor areconfigured to transmit, from an operating system (OS) to a modem, anindication of a start network request originating from an application,wherein the indication is based on a determination that a trafficdescriptor associated with the application is a non-default descriptor.In some examples, the memory and the processor are configured todetermine one or more parameters for establishing a new networkconnection for the application, the one or more parameters determinedbased on a routing policy that provides mapping between the trafficdescriptor and the one or more parameters. In some examples, the memoryand the processor are configured to transmit, to the application, anindication that the new network connection has been established based onthe one or more parameters.

Certain aspects are directed to an apparatus for wireless communication.In some examples, the apparatus includes means for transmitting, from anoperating system (OS) to a modem, an indication of a start networkrequest originating from an application, wherein the indication is basedon a determination that a traffic descriptor associated with theapplication is a non-default descriptor. In some examples, the apparatusincludes means for determining one or more parameters for establishing anew network connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters. In some examples, theapparatus includes means for transmitting, to the application, anindication that the new network connection has been established based onthe one or more parameters.

Certain aspects are directed to a non-transitory computer-readablemedium having instructions stored thereon that, when executed by a firstwireless device, cause the first wireless device to perform operations.In some examples, the operations include transmitting, from an operatingsystem (OS) to a modem, an indication of a start network requestoriginating from an application, the transmitting of the indicationbased on a determination that a traffic descriptor associated with theapplication is a non-default descriptor. In some examples, theoperations include determining one or more parameters for establishing anew network connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters. In some examples, theoperations include transmitting, to the application, an indication thatthe new network connection has been established based on the one or moreparameters.

Certain aspects are directed to a method for wireless communication at auser equipment (UE). In some examples, the method includes transmitting,from an operating system (OS) to a modem, an indication of a request toestablish a network connection originating from an application, therequest comprising a traffic descriptor associated with the networkconnection, the traffic descriptor provided by the application. In someexamples, the method includes transmitting, to the application, anindication that the network connection is established.

Certain aspects are directed to an apparatus for wireless communication.The apparatus includes a processor and a memory coupled to theprocessor. In some examples, the memory and the processor are configuredto transmit, from an operating system (OS) to a modem, an indication ofa request to establish a network connection originating from anapplication, the request comprising a traffic descriptor associated withthe network connection, the traffic descriptor provided by theapplication. In some examples, the memory and the processor areconfigured to transmit, to the application, an indication that thenetwork connection is established.

Certain aspects are directed to an apparatus for wireless communication.In some examples, the apparatus includes means for transmitting, from anoperating system (OS) to a modem, an indication of a request toestablish a network connection originating from an application, therequest comprising a traffic descriptor associated with the networkconnection, the traffic descriptor provided by the application. In someexamples, the apparatus includes means for transmitting, to theapplication, an indication that the network connection is established.

Certain aspects are directed to a non-transitory computer-readablemedium having instructions stored thereon that, when executed by a firstwireless device, cause the first wireless device to perform operations.In some examples, the operations include transmitting, from an operatingsystem (OS) to a modem, an indication of a request to establish anetwork connection originating from an application, the requestcomprising a traffic descriptor associated with the network connection,the traffic descriptor provided by the application. In some examples,the operations include transmitting, to the application, an indicationthat the network connection is established.

Certain aspects are directed to a method for wireless communication at auser equipment (UE). In some examples, the method includes receiving, bya modem, from an operating system (OS), a request for route identifier,the request for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated. In some examples, the method includestransmitting a route identifier to the OS, the route identifiergenerated by a modem based on a routing policy that provides mappingbetween the traffic descriptor and a network route. In some examples,the method includes receiving, by the modem, a start network requestcomprising the route identifier. In some examples, the method includesestablishing, in response to the start network request, a networkconnection via the network route.

Certain aspects are directed to an apparatus for wireless communication.In some examples, the apparatus includes a processor, a modem, and amemory coupled to the processor. In some examples, the processor and thememory are configured to receive, by the modem, from an operating system(OS), a request for route identifier, the request for route identifiercomprising a traffic descriptor corresponding to a first applicationfrom which the request for route identifier originated. In someexamples, the processor and the memory are configured to transmit aroute identifier to the OS, the route identifier generated by a modembased on a routing policy that provides mapping between the trafficdescriptor and a network route. In some examples, the processor and thememory are configured to receive, by the modem, a start network requestcomprising the route identifier. In some examples, the processor and thememory are configured to establish, in response to the start networkrequest, a network connection via the network route.

Certain aspects are directed to an apparatus for wireless communication.In some examples, the apparatus includes means for receiving, by amodem, from an operating system (OS), a request for route identifier,the request for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated. In some examples, the apparatus includes meansfor transmitting a route identifier to the OS, the route identifiergenerated by a modem based on a routing policy that provides mappingbetween the traffic descriptor and a network route. In some examples,the apparatus includes means for receiving, by the modem, a startnetwork request comprising the route identifier. In some examples, theapparatus includes means for establishing, in response to the startnetwork request, a network connection via the network route.

A non-transitory computer-readable medium having instructions storedthereon that, when executed by a first wireless device, cause the firstwireless device to perform operations. In some examples, the operationsinclude receiving, by a modem, from an operating system (OS), a requestfor route identifier, the request for route identifier comprising atraffic descriptor corresponding to a first application from which therequest for route identifier originated. In some examples, theoperations include transmitting a route identifier to the OS, the routeidentifier generated by a modem based on a routing policy that providesmapping between the traffic descriptor and a network route. In someexamples, the operations include receiving, by the modem, a startnetwork request comprising the route identifier. In some examples, theoperations include establishing, in response to the start networkrequest, a network connection via the network route.

Certain aspects of the subject matter described in this disclosure canbe implemented in a method for wireless communication by a userequipment (UE). The method may include storing, by a modem, a routeselection policy, the route selection policy associating each of aplurality of traffic descriptors with a corresponding data network name(DNN) and a corresponding slice, wherein a first traffic descriptor ofthe plurality of traffic descriptors is associated with a first DNN anda first slice, wherein a second traffic descriptor of the plurality oftraffic descriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default descriptor for the first DNN. The method may also includeexecuting, by one or more processors, an operating system and one ormore applications including an application. In some examples, theapplication is configured to send a request for a route identifier tothe operating system. In some examples, the operating system, based onreceiving the request for the route identifier, is configured to sendthe request for the route identifier to the modem with an applicationidentifier associated with the application. In some examples, the modem,based on receiving the request for the route identifier with theapplication identifier, is configured to generate the route identifierand associate the route identifier with the second traffic descriptor.In some examples, the modem is configured to send the route identifierto the operating system. In some examples, the operating system, basedon receiving the route identifier, is configured to send the routeidentifier to the application. In some examples, the application isconfigured to send a request to bring up an interface to the operatingsystem, the request to bring up the interface including the routeidentifier. In some examples, the operating system, based on receivingthe request to bring up the interface, is configured to determine if theinterface is already up based on the route identifier. In some examples,when the operating system determines the interface is already up, theoperating system is configured to send an identifier of the interface tothe application. In some examples, when the operating system determinesthe interface is not already up: the operating system is configured tosend a start network command to the modem, the start network commandincluding the route identifier. In some examples, the modem, based onreceiving the start network command, is configured to determine thefirst DNN and the second slice as associated with the route identifierbased on the route selection policy and establish a protocol data unit(PDU) session associated with the first DNN and the second slice. Insome examples, the modem is configured to send to the operating systeman indication of the PDU session establishment. In some examples, theoperating system, based on receiving the indication of the PDU sessionestablishment, is configured to set an interface status as up andassociated with the route identifier. In some examples, the operatingsystem is configured to send the identifier of the interface to theapplication. In some examples, the application is configured to utilizethe interface for communication.

Certain aspects of the subject matter described in this disclosure canbe implemented in a method for wireless communication by a userequipment (UE). The method may include storing, by a modem, a routeselection policy, the route selection policy associating each of aplurality of traffic descriptors with a corresponding data network name(DNN) and a corresponding slice, wherein a first traffic descriptor ofthe plurality of traffic descriptors is associated with a first DNN anda first slice, wherein a second traffic descriptor of the plurality oftraffic descriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default traffic descriptor for the first DNN. In certain aspects, oneor more processors configured to execute an operating system and one ormore applications including an application, wherein: the modem isconfigured to indicate any non-default traffic descriptors, includingthe second traffic descriptor, to the operating system. In someexamples, the application is configured to send a request to bring up aninterface to the operating system, the operating system is configuredto, based on receiving the request to bring up the interface, determineif a traffic descriptor associated with the application is a non-defaulttraffic descriptor indicated by the modem. In some examples, when thetraffic descriptor is not a non-default traffic descriptor, theoperating system is configured to indicate a first interface associatedwith default traffic descriptor to the application based on the requestto bring up the interface, and the application is configured to utilizethe first interface for communication. In some examples, when thetraffic descriptor is a non-default traffic descriptor and is the secondtraffic descriptor: the operating system is configured to send a routelookup to the modem, the route lookup including the second trafficdescriptor. In some examples, the modem is configured to, based onreceiving the route lookup, indicate a new interface is needed to theoperating system based on the second traffic descriptor being anon-default traffic descriptor. In some examples, the operating systemis configured to pick a second interface to perform the request to bringup the interface. In some examples, the operating system is configuredto send a start network command to the modem, the start network commandincluding the second traffic descriptor. In some examples, the modem,based on receiving the start network command, is configured to determinethe first DNN and the second slice as associated with the second trafficdescriptor based on the route selection policy and establish a protocoldata unit (PDU) session associated with the first DNN and the secondslice. In some examples, the modem is configured to send to theoperating system an indication of the PDU session establishmentincluding an identifier of the first DNN and an identifier of the secondslice. In some examples, the operating system, based on receiving theindication of the PDU session establishment, is configured to set asecond interface status as up and associated with the first DNN and thesecond slice. In some examples, the operating system is configured tosend an identifier of the second interface to the application. In someexamples, the application is configured to utilize the second interfacefor communication.

Certain aspects of the subject matter described in this disclosure canbe implemented in a method for wireless communication by a userequipment (UE). In some examples, the method includes a modem configuredto store a route selection policy, the route selection policyassociating each of a plurality of traffic descriptors with acorresponding data network name (DNN) and a corresponding slice, whereina first traffic descriptor of the plurality of traffic descriptors isassociated with a first DNN and a first slice, wherein a second trafficdescriptor of the plurality of traffic descriptors is associated withthe first DNN and a second slice different than the first slice, whereinthe first traffic descriptor is a default descriptor for the first DNN.In some examples, the method includes one or more processors configuredto execute an operating system and one or more applications including anapplication. In some examples, the application is configured to send arequest to bring up an interface to the operating system, the request tobring up the interface including a specifier indicating the first DNNand the second slice. In some examples, the operating system isconfigured to determine if the request to bring up the interfaceincludes any specifier. In some examples, the operating system isconfigured to, based on the request to bring up the interface includingthe specifier, send a start network command to the modem, the startnetwork command including the specifier. In some examples, the modem isconfigured to, based on receiving the start network command includingthe specifier, check if the route selection policy includes a trafficdescriptor associated with both the first DNN and the second slice. Insome examples, the modem is configured to, based on the route selectionpolicy including the second traffic descriptor associated with both thefirst DNN and the second slice, establish a protocol data unit (PDU)session associated with the first DNN and the second slice. In someexamples, the modem is configured to send to the operating system anindication of the PDU session establishment. In some examples, theoperating system, based on receiving the indication of the PDU sessionestablishment, is configured to set an interface status as up andassociated with the specifier. In some examples, the operating system isconfigured to send the identifier of the interface to the application.In some examples, the application is configured to utilize the interfacefor communication.

Aspects of the present disclosure provide means for, apparatus,processors, and computer-readable mediums for performing techniques andmethods that may be complementary to the operations by the UE describedherein, for example, by a BS.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

While aspects and embodiments are described in this application byillustration to some examples, those skilled in the art will understandthat additional implementations and use cases may come about in manydifferent arrangements and scenarios. Innovations described herein maybe implemented across many differing platform types, devices, systems,shapes, sizes, packaging arrangements. For example, embodiments and/oruses may come about via integrated chip embodiments and othernon-module-component based devices (e.g., end-user devices, vehicles,communication devices, computing devices, industrial equipment,retail/purchasing devices, medical devices, artificial intelligent (AI)enabled devices, etc.). While some examples may or may not bespecifically directed to use cases or applications, a wide assortment ofapplicability of described innovations may occur. Implementations mayrange in spectrum from chip-level or modular components to non-modular,non-chip-level implementations and further to aggregate, distributed, ororiginal equipment manufacturer (OEM) devices or systems incorporatingone or more aspects of the described innovations. In some practicalsettings, devices incorporating described aspects and features may alsonecessarily include additional components and features forimplementation and practice of claimed and described embodiments. Forexample, transmission and reception of wireless signals necessarilyincludes a number of components for analog and digital purposes (e.g.,hardware components including antenna, radio frequency (RF) chains,power amplifiers, modulators, buffer, processor(s), interleaver,adders/summers, etc.). It is intended that innovations described hereinmay be practiced in a wide variety of devices, chip-level components,systems, distributed arrangements, end-user devices, etc. of varyingsizes, shapes, and constitution.

The following description and the appended figures set forth certainfeatures for purposes of illustration.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the drawings. It is to be noted, however, thatthe appended drawings illustrate only certain typical aspects of thisdisclosure and are therefore not to be considered limiting of its scope,for the description may admit to other equally effective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram conceptually illustrating a design of anexample a base station (BS) and user equipment (UE), in accordance withcertain aspects of the present disclosure.

FIG. 3 is a call-flow diagram illustrating example signaling forestablishing a slice over which applications on a UE can communicate, inaccordance with certain aspects of the present disclosure.

FIG. 4 is a conceptual diagram illustrating a scenario wherecommunication to a same DNN occurs over two different slices, accordingto certain aspects disclosed herein.

FIG. 5 is a conceptual illustration of a UE route selection policy(URSP) configuration for supporting the communication scenarioillustrated in FIG. 4 , according to certain aspects disclosed herein.

FIG. 6 is a call-flow diagram illustrating a first example method forestablishing multi-slice communication between a UE and a network,according to certain aspects disclosed herein.

FIG. 7 is a call-flow diagram illustrating a second example method forestablishing multi-slice communication between a UE and a network, inaccordance with certain aspects of the present disclosure.

FIG. 8 is a call-flow diagram illustrating a third example method forestablishing multi-slice communication between a UE and a network, inaccordance with certain aspects of the present disclosure.

FIG. 9 is a call-flow diagram illustrating a fourth example method forestablishing multi-slice communication between a UE and a network, inaccordance with certain aspects of the present disclosure.

FIG. 10 is a flow diagram illustrating example operations for wirelesscommunication, in accordance with certain aspects of the presentdisclosure.

FIG. 11 is a flow diagram illustrating example operations for wirelesscommunication, in accordance with certain aspects of the presentdisclosure.

FIG. 12 is a flow diagram illustrating example operations for wirelesscommunication, in accordance with certain aspects of the presentdisclosure.

FIG. 13 illustrates a communications device that may include variouscomponents (e.g., corresponding to means-plus-function components)configured to perform operations for the techniques disclosed herein,such as the operations illustrated in FIG. 10 .

FIG. 14 illustrates a communications device that may include variouscomponents (e.g., corresponding to means-plus-function components)configured to perform operations for the techniques disclosed herein,such as the operations illustrated in FIG. 11 .

FIG. 15 illustrates a communications device that may include variouscomponents (e.g., corresponding to means-plus-function components)configured to perform operations for the techniques disclosed herein,such as the operations illustrated in FIG. 12 .

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for configuring a modem toprovide slicing, such as application-level slicing, and providing a userequipment (UE) with the capability to communicate over multi-slices.

The following description provides examples of communicating overmultiple slices in communication systems, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition to,or other than, the various aspects of the disclosure set forth herein.It should be understood that any aspect of the disclosure disclosedherein may be embodied by one or more elements of a claim. The word“exemplary” is used herein to mean “serving as an example, instance, orillustration.” Any aspect described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otheraspects.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a subcarrier, afrequency channel, a tone, a subband, etc. Each frequency may support asingle RAT in a given geographic area in order to avoid interferencebetween wireless networks of different RATs.

The techniques described herein may be used for various wirelessnetworks and radio technologies. While aspects may be described hereinusing terminology commonly associated with 3G, 4G, and/or new radio(e.g., 5G NR) wireless technologies, aspects of the present disclosurecan be applied in other generation-based communication systems.

NR access may support various wireless communication services, such asenhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80mega-hertz (MHz) or beyond), millimeter wave (mmW) targeting highcarrier frequency (e.g., 25 giga-hertz (GHz) or beyond), massive machinetype communications MTC (mMTC) targeting non-backward compatible MTCtechniques, and/or mission critical targeting ultra-reliable low-latencycommunications (URLLC). These services may include latency andreliability requirements. These services may also have differenttransmission time intervals (TTI) to meet respective quality of service(QoS) requirements. In addition, these services may co-exist in the samesubframe. NR supports beamforming and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells.

FIG. 1 illustrates an example wireless communication network 100 inwhich aspects of the present disclosure may be performed, for example,enabling application-based slice allocation in a multi-slice NR network.In some cases, the network 100 may be a multi-slice network, whereineach slice defines as a composition of adequately configured networkfunctions, network applications, and underlying cloud infrastructuresthat are bundled together to meet the requirement of a specific use caseor business model. For example, slices may include an enhanced mobilebroadband (eMBB) slice, an ultra-low latency communication (URLLC)slice, a massive Internet of things (mIoT) or massive machine-typecommunications (mMTC) slice, and any other suitable services.

The wireless communication network 100 may be an NR system (e.g., a 5GNR network). As shown in FIG. 1 , the wireless communication network 100may be in communication with a core network 132. The core network 132may in communication with one or more base station (BSs) 110 and/or userequipment (UE) 120 in the wireless communication network 100 via one ormore interfaces.

As illustrated in FIG. 1 , the wireless communication network 100 mayinclude a number of BSs 110 a-z (each also individually referred toherein as BS 110 or collectively as BSs 110) and other network entities.A BS 110 may provide communication coverage for a particular geographicarea, sometimes referred to as a “cell”, which may be stationary or maymove according to the location of a mobile BS 110. In some examples, theBSs 110 may be interconnected to one another and/or to one or more otherBSs or network nodes (not shown) in wireless communication network 100through various types of backhaul interfaces (e.g., a direct physicalconnection, a wireless connection, a virtual network, or the like) usingany suitable transport network. In the example shown in FIG. 1 , the BSs110 a, 110 b and 110 c may be macro BSs for the macro cells 102 a, 102 band 102 c, respectively. The BS 110 x may be a pico BS for a pico cell102 x. The BSs 110 y and 110 z may be femto BSs for the femto cells 102y and 102 z, respectively. A BS may support one or multiple cells. Anetwork controller 130 may couple to a set of BSs 110 and providecoordination and control for these BSs 110 (e.g., via a backhaul).

The BSs 110 communicate with UEs 120 a-y (each also individuallyreferred to herein as UE 120 or collectively as UEs 120) in the wirelesscommunication network 100. The UEs 120 (e.g., 120 x, 120 y, etc.) may bedispersed throughout the wireless communication network 100, and each UE120 may be stationary or mobile. Wireless communication network 100 mayalso include relay stations (e.g., relay station 110 r), also referredto as relays or the like, that receive a transmission of data and/orother information from an upstream station (e.g., a BS 110 a or a UE 120r) and sends a transmission of the data and/or other information to adownstream station (e.g., a UE 120 or a BS 110), or that relaystransmissions between UEs 120, to facilitate communication betweendevices.

According to certain aspects, the UEs 120 may be configured forcommunicating over multiple slices. For example, multiple applicationsexecuting on the UE 120 may each require a different slice forcommunication with a network. As shown in FIG. 1 , the UE 120 a includesa connection manager 122. In certain aspects, the connection manager 122may be configured to transmit, from an operating system (OS) to a modemof the UE 120, an indication of a start network request originating froman application executing on the OS. The transmission of the indicationmay be based on a determination that a traffic descriptor associatedwith the application is a non-default descriptor. In certain aspects,the connection manager 122 may determine one or more parameters forestablishing a new network connection for the application, the one ormore parameters determined based on a routing policy that providesmapping between the traffic descriptor and the one or more parameters.In certain aspects, connection manager 122 may transmit, to theapplication, an indication that the new network connection has beenestablished based on the one or more parameters.

In certain aspects, connection manager 122 may be configured totransmit, from an operating system (OS) to a modem, an indication of arequest to establish a network connection originating from anapplication, the request comprising a traffic descriptor associated withthe network connection, the traffic descriptor provided by theapplication. In certain aspects, connection manager 122 may beconfigured to transmit, to the application, an indication that thenetwork connection is established.

In certain aspects, a modem (e.g., modem 254 of FIG. 2 , modem 308 ofFIGS. 6-9 ) may be configured to receive, from an operating system (OS),a request for route identifier, the request for route identifiercomprising a traffic descriptor corresponding to a first applicationfrom which the request for route identifier originated. In certainaspects, the modem may be configured to transmit a route identifier tothe OS, the route identifier generated by the modem based on a routingpolicy that provides mapping between the traffic descriptor and anetwork route. In certain aspects, the modem is configured to receive astart network request comprising the route identifier. In certainaspects, the modem is configured to establish, in response to the startnetwork request, a network connection via the network route.

In certain aspects, the modem is configured to store a route selectionpolicy, the route selection policy associating each of a plurality oftraffic descriptors with a corresponding data network name (DNN) and acorresponding slice, wherein a first traffic descriptor of the pluralityof traffic descriptors is associated with a first DNN and a first slice,wherein a second traffic descriptor of the plurality of trafficdescriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default traffic descriptor for the first DNN, in accordance withaspects of the present disclosure. In some examples, the connectionmanager 122 may execute, by one or more processors, an operating systemand one or more applications including an application.

FIG. 2 illustrates example components 200 of BS 110 a and UE 120 a(e.g., in the wireless communication network 100 of FIG. 1 ), which maybe used to implement aspects of the present disclosure.

At the BS 110 a, a transmit processor 220 may receive data from a datasource 212 and control information from a controller/processor 240. Thecontrol information may be for the physical broadcast channel (PBCH),physical control format indicator channel (PCFICH), physical hybridautomatic repeat request (HARM) indicator channel (PHICH), physicaldownlink control channel (PDCCH), group common (GC) PDCCH, etc. The datamay be for the physical downlink shared channel (PDSCH), etc. A mediumaccess control (MAC)-control element (MAC-CE) is a MAC layercommunication structure that may be used for control command exchangebetween wireless nodes. The MAC-CE may be carried in a shared channelsuch as a physical downlink shared channel (PDSCH), a physical uplinkshared channel (PUSCH), or a physical sidelink shared channel (PSSCH).

The processor 220 may process (e.g., encode and symbol map) the data andcontrol information to obtain data symbols and control symbols,respectively. The transmit processor 220 may also generate referencesymbols, such as for the primary synchronization signal (PSS), secondarysynchronization signal (SSS), and channel state information referencesignal (CSI-RS). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, and/or the reference symbols, ifapplicable, and may provide output symbol streams to the modulators(MODs) 232 a-232 t. Each modulator 232 may process a respective outputsymbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.Each modulator may further process (e.g., convert to analog, amplify,filter, and upconvert) the output sample stream to obtain a downlinksignal. Downlink signals from modulators 232 a-232 t may be transmittedvia the antennas 234 a-234 t, respectively.

At the UE 120 a, the antennas 252 a-252 r may receive the downlinksignals from the BS 110 a and may provide received signals to thedemodulators (DEMODs) in transceivers 254 a-254 r, respectively. Eachdemodulator 254 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator may further process the input samples (e.g., for OFDM, etc.)to obtain received symbols. A MIMO detector 256 may obtain receivedsymbols from all the demodulators 254 a-254 r, perform MIMO detection onthe received symbols if applicable, and provide detected symbols. Areceive processor 258 may process (e.g., demodulate, deinterleave, anddecode) the detected symbols, provide decoded data for the UE 120 a to adata sink 260, and provide decoded control information to acontroller/processor 280. In some examples, demodulators 254 a-254 r areconfigured to function as modems.

On the uplink, at UE 120 a, a transmit processor 264 may receive andprocess data (e.g., for the physical uplink shared channel (PUSCH)) froma data source 262 and control information (e.g., for the physical uplinkcontrol channel (PUCCH) from the controller/processor 280. The transmitprocessor 264 may also generate reference symbols for a reference signal(e.g., for the sounding reference signal (SRS)). The symbols from thetransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modulators in transceivers 254a-254 r (e.g., for SC-FDM, etc.), and transmitted to the BS 110 a. Atthe BS 110 a, the uplink signals from the UE 120 a may be received bythe antennas 234, processed by the modulators 232, detected by a MIMOdetector 236 if applicable, and further processed by a receive processor238 to obtain decoded data and control information sent by the UE 120 a.The receive processor 238 may provide the decoded data to a data sink239 and the decoded control information to the controller/processor 240.

The memories 242 and 282 may store data and program codes for BS 110 aand UE 120 a, respectively. A scheduler 244 may schedule UEs for datatransmission on the downlink and/or uplink.

Antennas 252, processors 266, 258, 264, and/or controller/processor 280of the UE 120 a and/or antennas 234, processors 220, 230, 238, and/orcontroller/processor 240 of the BS 110 a may be used to perform thevarious techniques and methods described herein. As shown in FIG. 2 ,the controller/processor 280 of the UE 120 a has the connection manager122. In some examples, the connection manager 122 may be executed on ahigh level operating system (HLOS) running on a controller/processor. Insome examples, one or more applications may execute on top of the HLOS.

NR may utilize orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) on the uplink and downlink. NR may supporthalf-duplex operation using time division duplexing (TDD). OFDM andsingle-carrier frequency division multiplexing (SC-FDM) partition thesystem bandwidth into multiple orthogonal subcarriers, which are alsocommonly referred to as tones, bins, etc. Each subcarrier may bemodulated with data. Modulation symbols may be sent in the frequencydomain with OFDM and in the time domain with SC-FDM. The spacing betweenadjacent subcarriers may be fixed, and the total number of subcarriersmay be dependent on the system bandwidth. The minimum resourceallocation, called a resource block (RB), may be 12 consecutivesubcarriers. The system bandwidth may also be partitioned into subbands.For example, a sub-band may cover multiple RBs. NR may support a basesubcarrier spacing (SCS) of 15 kilo-hertz (KHz) and other SCS may bedefined with respect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240kHz, etc.).

Example Method for Establishing a Slice Per UE

FIG. 3 is a call flow diagram illustrating example signaling 300 forestablishing multiple slices over which applications (apps) on a UE(e.g., UE 120 a of FIGS. 1 and 2 ) can communicate. In this example, theUE 120 a includes a controller/processor (e.g., controller/processor 280of FIG. 2 ) and a modem 308 (e.g., modem 254 of FIG. 2 ). The controllerprocessor 280 supports a high-level operating system (HLOS) upon whichmultiple applications (e.g., a first app 302 and a second app 304)execute. In some examples, the HLOS includes a connection manager 306,which may be any suitable operating system component capable ofcommunication between the applications (302 and 304) and the modem 308.The modem 308 may be configured to communicate between a network 310(e.g., BS 110 a of FIGS. 1 and 2 ) and the HLOS connection manager 306.

The first application 302 and the second application 304 on the UE 120 amay communicate with the network 310 via the HLOS connection manager 306and the modem 308. In some examples, the modem 308 is configured toidentify an app which is the source/destination of a data packet. Forexample, the association between the data packet and the application maybe identified by having the HLOS pass an app identifier, or app ID(e.g., APP_1 for the first app 302, and APP_2 for the second app 304) ofthe application along with the data packet. Each data packet may betagged with the identifier. That is, the data packet may be communicatedfrom the HLOS to the modem along with an identifier (e.g., a tag) as anauxiliary data field which associates the data packet with theapplication.

Initially, upon power up of the UE 120 a, there is no connectedinterface between the UE 120 a and the network 310. Accordingly, themodem 308 and the network 310 perform a modem initialization 312 whereina registration is performed between the modem 308 and the network 310.In an HLOS internet establishment 314, the HLOS connection manager 306and the modem communicate to establish a connection interface betweenthe UE 120 a and the network 310. Prior to performing the HLOS internetestablishment 314, the HLOS connection manager 306 may look up an accesspoint name (APN) for an Internet type connection, wherein the APN isstored in a database maintained by the HLOS connection manager 306. TheHLOS connection manager 306 may then confirm that the APN is configuredin a modem profile database maintained by the modem 308.

In some embodiments, the modem 308 does not establish an internetconnection to facilitate internet communication between the modem 308and the network 310 at the modem initialization 312. As such, in theHLOS internet establishment 314, the HLOS connection manager 306requests that the modem 308 start an internet interface with the network310. Upon receiving the request, the modem 308 may check a UE routeselection policy (URSP) received from the network 310 during the modeminitialization 312 to determine a data network name (DNN) and slice forthe Internet type connection with the APN. The URSP provides the modemwith default slice for the Internet type connection with the APN. Themodem 308 can then establish a protocol data unit (PDU) session with thenetwork 310 to establish the Internet type connection using the eMBBslice. Once the PDU session is established, the modem 308 may notify theHLOS connection manager 306 that the session is established.

Once the network internet interface is established during the HLOSinternet establishment 314, an internet data path pipe is establishedbetween the HLOS connection manager 306, the modem 308, and the network310. Thus, the first application 302 and the second application 304 canbegin to use the internet data path pipe to communicate data between theapplications and the network 310.

As such, one slice may be used for the each UE 120 a, or alternatively,one slice for each DNN of the UE 120 a. For example, a single UE 120 amay use multiple DNNs (e.g., an admin data network, an internet datanetwork, an IP multimedia system (IMS) data network, etc.), wherein eachof the multiple DNNs use the same slice (e.g., eMBB slice).

However, certain applications on a UE 120 a may desire to use adifferent slice for a DNN such as the Internet, such as URLLC, which maynot function correctly if the UE 120 a can only be configured to use asingle eMBB slice for the Internet. As such, it would be advantageous toprovide the UE 120 a with the ability to use multiple slices. In someexamples, it would be advantageous if the UE 120 a had the ability toestablish connections over multiple slices with a single DNN.

Example Methods for Establishing Multiple Slices Per UE

FIG. 4 is a conceptual diagram illustrating a scenario wherecommunication to a same DNN occurs over two different slices (e.g., aneMBB slice 402 and a URLLC slice 404), according to certain aspectsdisclosed herein. The UE 120 a may include multiple applications (e.g.,first app 302 and second app 304 of FIG. 3 ). The UE 120 a may beconfigured to communicate data with a network (e.g., network 310 of FIG.3 ), wherein the network may include N data networks, (e.g., a first DNN“internet data network” 406 through “N” DNN 406 n) where N is a non-zerointeger. Here, the first app 302 is configured to communicate over theeMBB slice 402 with the internet data network 406 DNN, such as based ona first traffic descriptor (e.g., default used for Internetcommunication) that is specified in the URSP of the UE 120 a. On theother hand, the second app 304 is configured to communicate over theURLLC slice 404 with the internet data network 406 DNN based on a secondtraffic descriptor of the second app 304 that is specified in the URSP.

That is, the URSP policy indicates that by default apps such as thefirst app 302 should be communicatively connected to the first DNN viathe eMBB slice 402, while the second app 304, which has a specifictraffic descriptor in a universal route selection policy (USRP) thatsupersedes a default policy, should be communicatively connected to thefirst DNN via the URLLC slice 404.

FIG. 5 is a conceptual illustration of a URSP configuration 500 forsupporting the communication scenario illustrated in FIG. 4 . The URSPconfiguration 500 may include multiple rules indexed by a trafficdescriptor. For example, a first rule 505 may be indexed by trafficdescriptor “DNN_Internet.” A second rule 510 may be indexed by trafficdescriptor “APP_2.” A third rule 515 may be indexed by trafficdescriptor “DNN_IMS,” and a fourth rule 520 may be indexed by trafficdescriptor “DNN_Admin.” As shown, each rule may include one or more of acorresponding slice, a corresponding session and service continuity(SSC) mode, an access type, and/or a priority. Additional identifiers,modes, types, etc. may also be added to the rules without departing fromthe novel features disclosed herein.

In this example, the traffic descriptor for each of the first rule 505,the third rule 515, and the fourth rule 520 may be a particular DNN. Forexample, the traffic descriptor for the first rule 505 may be anInternet DNN, the traffic descriptor for the third rule 515 may be inIMS DNN, and the traffic descriptor for the fourth rule 520 may be anadministrator DNN. These traffic descriptors may serve as defaults forcommunication over the corresponding DNN. In contrast, the trafficdescriptor for the second rule 510 may be an APN, an app ID, or anyother suitable identifier associated with, for example, second app 304.

FIG. 6 is a call flow diagram 600 illustrating a first example methodfor establishing multi-slice communication between a UE 120 a and anetwork 310. In accordance with various aspects of the disclosure, anelement of FIG. 6 , or any portion of an element, or any combination ofelements may be implemented with the controller/processor 280 and/ormodem 254 of FIG. 2 that includes one or more processors.

At the outset, the modem initialization 312 and the HLOS internetestablishment 314 may be the same as shown in FIG. 3 as described above,wherein an internet data path pipe via eMBB (not shown) is established.In some examples, the second app 304 is configured to request a routeidentifier, also referred to as a cookie, from the HLOS connectionmanager 306.

The HLOS connection manager 306 may determine that the request is fromsecond app 304, and determine a traffic descriptor, such as app ID APP_2of the second app 304, and pass the request along with the trafficdescriptor to the modem 308, which may then determine a route (e.g., aninternet data pipe via URLLC slice) for the second app 304, and generatea cookie (e.g., a string, such as a random string, hash, etc. of one ormore values) for the second app 304. For example, the modem 308, basedon the URSP configuration 500, associates the traffic descriptor APP_2sent with the request, with second rule 510, and thus slice URLLC. Themodem 308 then associates the cookie with the determined route. Themodem 308 may then provide the HLOS connection manager 306 with thecookie that provides a mapping to the determined route, such as in adatabase maintained by the modem 308. In some examples, the database mayindex each route stored on the database according to a correspondingcookie. The HLOS connection manager 306 provides the cookie to thesecond app 304. It should be noted that in certain aspects, since thecookie may be a random string, only the modem may specifically knowwhich route maps with which cookie, and HLOS connection manager 306and/or second app 304 do not need to have such knowledge or ability tomake such a determination.

Next, the second application 304 may bring up an interface to thenetwork 310 via the route associated with the cookie, and thus via theURLLC slice. In some examples, the second application 304 maycommunicate a bring-up command along with the cookie to HLOS connectionmanager 306 to bring up the route. In certain aspects, such as tomaintain consistency with legacy functions, the second application 304may also communicate the DNN for the route along with the bring-upcommand.

The HLOS connection manager 306 may then determine if there is alreadyan interface associated with the cookie (e.g., and DNN) requested by thesecond app 304. If there is already an interface, then the HLOSconnection manager 306 will map the second app 304 to the existinginterface.

However, if there is no existing interface, the HLOS connection manager306 will communicate a start network (e.g., “start NW”) request to themodem 308 that includes the cookie (e.g., and the DNN). When the requestis received, the modem 308 will respond by looking up the route (i.e.,that is over URLLC in this case) associated with the cookie (e.g., andthe identified data network), and setting up a PDU session for theroute. Once modem 308 determines that the PDU session is established,the modem 308 may notify the HLOS connection manager 306 that therequested interface via the route is established. The HLOS connectionmanager 306 may then proceed to notify the second app 304 that thenetwork is up. The second app 304 may then proceed to communicate withthe network 310 over the URLLC slice. Thus, at this point, there are twointerfaces established between the UE 120 a and the internet DNN fornetwork 310: an internet data path pipe via the eMBB slice (default),and an internet data path pipe via the URLLC slice (e.g., associatedwith the cookie).

Although the examples provided herein relate to a request by the secondapp 304 that includes both a cookie and an identification of the datanetwork, it is appreciated that the second app 304 may instead providethe request with only the cookie.

The modem 308 may then communicate a “connected” service status to thesecond app 304 via the HLOS connection manager 306, and the second app304 may begin communications over the internet data pipe via the URLLCslice.

It should be noted that, in the example described above, and inreference to FIG. 6 , in some examples, the cookie string generated bythe modem 308 is a random string. In some examples, the app ID mayinclude one of an application identifier of the application or a remoteInternet protocol (IP) address associated with the application.Moreover, to the extent that the foregoing examples relate to eMBB andURLLC slices, it is appreciated that these slices may include any otherservices, including MIoT; and to the extent that the data networkdescribed in the foregoing is an Internet data network, any othersuitable data network or service may be used (e.g., administrative datanetwork IMS data network, etc.).

FIG. 7 is a call flow diagram 700 illustrating a second example methodfor establishing multi-slice communication between a UE 120 a and anetwork 310. In accordance with various aspects of the disclosure, anelement of FIG. 7 , or any portion of an element, or any combination ofelements may be implemented with the controller/processor 280 and/ormodem 254 of FIG. 2 that includes one or more processors.

At the outset, the modem initialization 312 and the HLOS internetestablishment 314 may be the same as shown in FIG. 3 as described above,wherein an internet data path pipe via eMBB (not shown) is established.However, in this example, the modem 308 may be configured to provide theHLOS connection manager 306 with an indication of any non-defaulttraffic descriptors (e.g., app ID (e.g., APP2), IP address of aparticular server, etc.). In response the HLOS connection manager 306may install an application traffic descriptor corresponding to thenon-default traffic descriptors.

The second app 304 may then request, from the HLOS connection manager306, to bring up a connection, such as an Internet connection, therequest indicating a service and/or DNN for the connection. In responsethe HLOS connection manager 306 determines a traffic descriptorassociated with the second app 304, and may determine whether thetraffic descriptor is a non-default traffic descriptor, as indicated bythe modem 308. If the traffic descriptor is not a non-default trafficdescriptor, then the HLOS connection manager 306 may configure thesecond app 304 for communication over a default connection, such as theinternet data path pipe via the eMBB slice.

However, if the HLOS connection manager 306 determines that the trafficdescriptor of the second app 304 is a non-default traffic descriptor,the HLOS connection manager 306 may notify the modem 308 of the request.In response, the modem 308 may notify the HLOS connection manger 306 toutilize one of: (i) the existing internet data path pipe via the eMBBslice, or (ii) a new interface is required. For example, if the trafficdescriptor of the second app 304 maps to a URSP rule that indicates aURLLC slice, then a new interface will be required.

In response to a notification that a new interface is required, the HLOSconnection manager 306 may pick a new interface (e.g., determine a datanetwork and slice of the new interface) and request the modem 308 tostart the new interface. Alternatively, if a new interface is required,the modem may inform the HLOS connection manage 306 of a DNN and a slicecombination of the new interface. In some examples, the request to startthe new interface may include the traffic descriptor, which, in anexample is an app ID corresponding to the second app.

In response to the HLOS connection manager 306, the modem 308 may checkthe URSP for the data network and the slice corresponding to the trafficdescriptor, and establish a PDU session with the network 310 accordingto the information of the traffic descriptor. Once the PDU session isestablished, the modem 308 may notify the HLOS connection manager 306that the service is connected. The HLOS connection manager 306 maynotify the second application of the same, and the second app 304 maythen proceed to communicate using an internet data pipe via the URLLCslice.

FIG. 8 is a call flow diagram 800 illustrating a third example methodfor establishing multi-slice communication between a UE 120 a and anetwork 310. In accordance with various aspects of the disclosure, anelement of FIG. 8 , or any portion of an element, or any combination ofelements may be implemented with the controller/processor 280 and/ormodem 254 of FIG. 2 that includes one or more processors.

At the outset, the modem initialization 312 and the HLOS internetestablishment 314 may be the same as shown in FIG. 3 as described above,wherein an internet data path pipe via eMBB (not shown) is established.However, in this example, the second app 304 may communicate a requestto the HLOS connection manager 306 requesting an internet connection viaa URLLC slice. The request includes a specifier identifying the servicerequested (e.g., internet) and the corresponding slice (e.g., URLLC).The specifier can be any value or string that the modem can map to a DNNand/or APN of a data network and a slice. Accordingly, the second app304 itself can specifically request a particular DNN with a particularslice. In certain embodiments, the request also includes a DNN.

The HLOS connection manager 306 may then determine if the specifierexists in a database managed by the HLOS connection manager 306. Forexample, the HLOS connection manager 306 may look up the specifier inthe database and determine a corresponding DNN/APN associated with thespecifier. The HLOS connection manager 306 may then communicate theDNN/APN to the modem 308, along with the specifier and/or an indicationof the slice, in a request to start a network connection according tothe request by the second application 304.

The modem 308 may then check the URSP to determine whether the requestedslice (e.g., URLLC) is allowed or available from the network 310 for theservice/DNN indicated. If the URSP does not indicate that the requestedslice can be used for the corresponding service, the modem 308 may denya PDU session establishment. However, if the URSP indicates that therequested slice can be used for the corresponding service, the modem 308may establish a PDU session for the second app 304, and notify the HLOSconnection manager 306 when the PDU session is established. The HLOSconnection manager 306 may then notify the second app 304 of theconnection establishment (e.g., establishment of the internet data pathpipe via the URLLC slice), and the second app 304 may communicate overthe internet data path pipe via the URLLC slice.

FIG. 9 is a call flow diagram 900 illustrating a fourth example methodfor establishing multi-slice communication between a UE 120 a and anetwork 310. In accordance with various aspects of the disclosure, anelement of FIG. 9 , or any portion of an element, or any combination ofelements may be implemented with the controller/processor 280 and/ormodem 254 of FIG. 2 that includes one or more processors.

FIG. 9 is a variation of the method shown in FIG. 8 , wherein the HLOSconnection manager 306 immediately proceeds to request the modem 308 tostart a network based on a request form the second app 304. In thisexample, the HLOS connection manager 306 does not first look up thespecifier in the database to determine whether there is a correspondingAPN associated with the specifier. Instead, the HLOS connection manager306 passes the information provided by the second app 304 to the modem308.

FIG. 10 is a flow diagram illustrating example operations 1000 forwireless communication, in accordance with certain aspects of thepresent disclosure. The operations 1000 may be performed, for example,by a UE (e.g., such as the UE 120 a in the wireless communicationnetwork 100 of FIG. 1 ). Operations 1000 may be implemented as softwarecomponents that are executed and run on one or more processors (e.g.,controller/processor 280 of FIG. 2 ) and/or a modem (e.g., modem 254 ofFIG. 2 ). Further, the transmission and reception of signals by the UEin operations 1000 may be enabled, for example, by one or more antennas(e.g., antennas 252 of FIG. 2 ). In certain aspects, the transmissionand/or reception of signals by the UE may be implemented via a businterface of one or more processors (e.g., controller/processor 280)obtaining and/or outputting signals.

The operations 1000 may begin, at block 1005, by transmitting, from anoperating system (OS) to a modem, an indication of a start networkrequest originating from an application, the transmitting of theindication based on a determination that a traffic descriptor associatedwith the application is a non-default descriptor.

The operations 1000 may proceed at block 1010, by determining one ormore parameters for establishing a new network connection for theapplication, the one or more parameters determined based on a routingpolicy that provides mapping between the traffic descriptor and the oneor more parameters.

The operations 1000 may proceed at block 1015, by transmitting, to theapplication, an indication that the new network connection has beenestablished based on the one or more parameters.

In certain aspects, the operations 1000 include receiving, from themodem, an application descriptor list comprising one or more trafficdescriptors that are non-default descriptors, the one or more trafficdescriptors comprising an application identifier associated with theapplication, wherein any traffic descriptor not on the applicationdescriptor list is a default descriptor.

In certain aspects, the default descriptor is associated with a firstDNN and a first network slice, wherein the non-default descriptor isassociated with the first DNN and a second network slice, and whereinthe default descriptor is a default descriptor for the first DNN.

In certain aspects, the non-default descriptor indicates that theapplication communicates via the second network slice.

In certain aspects, the operations 1000 include determining, by the OS,that the traffic descriptor associated with the application is thenon-default descriptor, wherein the determination indicates that theapplication has permission from the modem to communicate via the secondnetwork slice.

In certain aspects, the one or more parameters comprise one or more of adata network name (DNN) or a network slice, wherein each of the DNN andthe network slice are associated with the traffic descriptor.

In certain aspects, the operations 1000 include transmitting, to themodem, a command to establish the new network connection, the commandcomprising the one or more parameters.

In certain aspects, the operations 1000 include receiving, from themodem, the indication that the new network connection has beenestablished, and wherein transmitting the indication to the applicationis in response to receiving the indication from the modem.

In certain aspects, the operations 1000 include storing, by a modem, aroute selection policy, the route selection policy associating each of aplurality of traffic descriptors with a corresponding data network name(DNN) and a corresponding slice, wherein a first traffic descriptor ofthe plurality of traffic descriptors is associated with a first DNN anda first slice, wherein a second traffic descriptor of the plurality oftraffic descriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default descriptor for the first DNN.

In certain aspects, the operations 1000 include executing, by one ormore processors, an operating system and one or more applicationsincluding an application, wherein: the application is configured to senda request for a route identifier to the operating system; the operatingsystem, based on receiving the request for the route identifier, isconfigured to send the request for the route identifier to the modemwith an application identifier associated with the application; themodem, based on receiving the request for the route identifier with theapplication identifier, is configured to generate the route identifierand associate the route identifier with the second traffic descriptor;the modem is configured to send the route identifier to the operatingsystem; the operating system, based on receiving the route identifier,is configured to send the route identifier to the application; theapplication is configured to send a request to bring up an interface tothe operating system, the request to bring up the interface includingthe route identifier; the operating system, based on receiving therequest to bring up the interface, is configured to determine if theinterface is already up based on the route identifier; when theoperating system determines the interface is already up, the operatingsystem is configured to send an identifier of the interface to theapplication; when the operating system determines the interface is notalready up: the operating system is configured to send a start networkcommand to the modem, the start network command including the routeidentifier; the modem, based on receiving the start network command, isconfigured to determine the first DNN and the second slice as associatedwith the route identifier based on the route selection policy andestablish a protocol data unit (PDU) session associated with the firstDNN and the second slice; the modem is configured to send to theoperating system an indication of the PDU session establishment; theoperating system, based on receiving the indication of the PDU sessionestablishment, is configured to set an interface status as up andassociated with the route identifier; and the operating system isconfigured to send the identifier of the interface to the application;and the application is configured to utilize the interface forcommunication.

In certain aspects, the request to bring up the interface furtherincludes an identifier of the first DNN, wherein the start networkcommand further includes the identifier of the first DNN.

In certain aspects, the modem generates the route identifier as a randomstring.

In certain aspects, the application does not have a mapping of the routeidentifier to the second slice.

In certain aspects, the second traffic descriptor is one of anapplication identifier of the application or a remote Internet protocol(IP) address associated with the application.

In certain aspects, the first slice is enhanced Mobile Broadband (eMBB),and wherein the second slice is one of Ultra-Reliable Low LatencyCommunications (URLLC) or massive Internet of Things (MIoT).

In certain aspects, wherein the first DNN is the Internet.

FIG. 11 is a flow diagram illustrating example operations 1100 forwireless communication, in accordance with certain aspects of thepresent disclosure. The operations 1100 may be performed, for example,by a UE (e.g., such as the UE 120 a in the wireless communicationnetwork 100 of FIG. 1 ). Operations 1100 may be implemented as softwarecomponents that are executed and run on one or more processors (e.g.,controller/processor 280 of FIG. 2 ) and/or a modem (e.g., modem 254 ofFIG. 2 ). Further, the transmission and reception of signals by the UEin operations 1100 may be enabled, for example, by one or more antennas(e.g., antennas 252 of FIG. 2 ). In certain aspects, the transmissionand/or reception of signals by the UE may be implemented via a businterface of one or more processors (e.g., controller/processor 280)obtaining and/or outputting signals.

The operations 1100 may begin, at block 1105, by transmitting, from anoperating system (OS) to a modem, an indication of a request toestablish a network connection originating from an application, therequest comprising a traffic descriptor associated with the networkconnection, the traffic descriptor provided by the application.

The operations 1100 may proceed, at block 1110, by transmitting, to theapplication, an indication that the network connection is established.

In certain aspects, the traffic descriptor is indicative of one or moreof a service requested for the network connection and a network sliceassociated with the network connection.

In certain aspects, the operations 1100 include determining whether thetraffic descriptor exists in a database maintained by the OS, wherein ifthe traffic descriptor exists in the database, the method furthercomprises transmitting, to the modem, one or more of a data network name(DNN) or an access point name (APN) associated with the trafficdescriptor in the database, and wherein if the traffic descriptor doesnot exist in the database, the method further comprises transmitting, tothe modem, the traffic descriptor.

In certain aspects, the traffic descriptor comprises one or more of adata network name (DNN) or an access point name (APN) associated withthe network connection.

In certain aspects, the operations 1100 include receiving, from themodem, the indication that the network connection is established priorto transmitting the indication to the application, wherein the receivingthe indication implicitly indicates that the modem approved the networkconnection.

In certain aspects, the operations 1100 include approving, by the modem,the network connection based on a routing policy that provides mappingbetween the traffic descriptor provided by the application and a datanetwork name (DNN) or an access point name (APN) associated with thetraffic descriptor.

In certain aspects, the operations 1100 include storing, by a modem, aroute selection policy, the route selection policy associating each of aplurality of traffic descriptors with a corresponding data network name(DNN) and a corresponding slice, wherein a first traffic descriptor ofthe plurality of traffic descriptors is associated with a first DNN anda first slice, wherein a second traffic descriptor of the plurality oftraffic descriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default traffic descriptor for the first DNN.

In certain aspects, the operations 1100 include executing, by one ormore processors, an operating system and one or more applicationsincluding an application, wherein: the modem is configured to indicateany non-default traffic descriptors, including the second trafficdescriptor, to the operating system; the application is configured tosend a request to bring up an interface to the operating system, theoperating system is configured to, based on receiving the request tobring up the interface, determine if a traffic descriptor associatedwith the application is a non-default traffic descriptor indicated bythe modem; when the traffic descriptor is not a non-default trafficdescriptor, the operating system is configured to indicate a firstinterface associated with default traffic descriptor to the applicationbased on the request to bring up the interface, and the application isconfigured to utilize the first interface for communication; and whenthe traffic descriptor is a non-default traffic descriptor and is thesecond traffic descriptor: the operating system is configured to send aroute lookup to the modem, the route lookup including the second trafficdescriptor; the modem is configured to, based on receiving the routelookup, indicate a new interface is needed to the operating system basedon the second traffic descriptor being a non-default traffic descriptor;the operating system is configured to pick a second interface to performthe request to bring up the interface; the operating system isconfigured to send a start network command to the modem, the startnetwork command including the second traffic descriptor; the modem,based on receiving the start network command, is configured to determinethe first DNN and the second slice as associated with the second trafficdescriptor based on the route selection policy and establish a protocoldata unit (PDU) session associated with the first DNN and the secondslice; the modem is configured to send to the operating system anindication of the PDU session establishment including an identifier ofthe first DNN and an identifier of the second slice; the operatingsystem, based on receiving the indication of the PDU sessionestablishment, is configured to set the second interface status as upand associated with the first DNN and the second slice; and theoperating system is configured to send an identifier of the secondinterface to the application; and the application is configured toutilize the second interface for communication.

In certain aspects, the second traffic descriptor is one of anapplication identifier of the application or a remote Internet protocol(IP) address associated with the application.

In certain aspects, the first slice is enhanced mobile broadband (eMBB),and wherein the second slice is one of ultra-reliable low latencycommunications (URLLC) or massive internet of things (MIoT).

FIG. 12 is a flow diagram illustrating example operations 1200 forwireless communication, in accordance with certain aspects of thepresent disclosure. The operations 1200 may be performed, for example,by a UE (e.g., such as the UE 120 a in the wireless communicationnetwork 100 of FIG. 1 ). Operations 1200 may be implemented as softwarecomponents that are executed and run on one or more processors (e.g.,controller/processor 280 of FIG. 2 ) and/or a modem (e.g., modem 254 ofFIG. 2 ). Further, the transmission and reception of signals by the UEin operations 1200 may be enabled, for example, by one or more antennas(e.g., antennas 252 of FIG. 2 ). In certain aspects, the transmissionand/or reception of signals by the UE may be implemented via a businterface of one or more processors (e.g., controller/processor 280)obtaining and/or outputting signals.

The operations 1200 may begin, at block 1205, by receiving, by themodem, from an operating system (OS), a request for route identifier,the request for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated.

The operations 1200 may proceed, at block 1210, by transmitting a routeidentifier to the OS, the route identifier generated by a modem based ona routing policy that provides mapping between the traffic descriptorand a network route.

The operations 1200 may proceed, at block 1215, by receiving, by themodem, a start network request comprising the route identifier.

The operations 1200 may proceed, at block 1220, by establishing, inresponse to the start network request, a network connection via thenetwork route.

In certain aspects, the routing policy provides mapping between each ofa plurality of traffic descriptors and a corresponding network route,and wherein each corresponding network route comprises a data networkname (DNN) and an indication of a network slice.

In certain aspects, a first traffic descriptor of the plurality oftraffic descriptors is associated with a first DNN and a first networkslice, wherein a second traffic descriptor of the plurality of trafficdescriptors is associated with the first DNN and a second network slice,and wherein the first traffic descriptor is a default descriptor for thefirst DNN.

In certain aspects, transmitting the route identifier to the OSindicates that the first application has permission from the modem tocommunicate via the second network slice.

In certain aspects, establishing the network connection furthercomprises: determining, by the modem, a first data network name and afirst network slice associated with the route identifier; andestablishing a protocol data unit (PDU) session associated with thefirst DNN via the first network slice.

In certain aspects, the operations 1200 include storing an index mappingthe network route to the generated route identifier, wherein the routeidentifier is a random string of one or more values.

In certain aspects, the traffic descriptor is added to the request forroute identifier by the OS.

In certain aspects, the start network request originates from the firstapplication, the method further comprising: receiving, by the OS, thestart network request from the first application; in response toreceiving the start network request, determining whether an existingnetwork connection corresponding to the route identifier is available;when the existing network connection is available, enabling, by the OS,the first application for communication over the existing networkconnection; and when the existing network connection is not available,transmitting the start network request to the modem.

In certain aspects, the operations 1200 include notifying the OS, by themodem, that the network connection has been established.

The operations 1200 may include storing, by a modem, a route selectionpolicy, the route selection policy associating each of a plurality oftraffic descriptors with a corresponding data network name (DNN) and acorresponding slice, wherein a first traffic descriptor of the pluralityof traffic descriptors is associated with a first DNN and a first slice,wherein a second traffic descriptor of the plurality of trafficdescriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default descriptor for the first DNN.

The operations 1200 may include executing, by one or more processors, anoperating system and one or more applications including an application,wherein: the application is configured to send a request to bring up aninterface to the operating system, the request to bring up the interfaceincluding a specifier indicating the first DNN and the second slice; theoperating system is configured to determine if the request to bring upthe interface includes any specifier; the operating system is configuredto, based on the request to bring up the interface including thespecifier, send a start network command to the modem, the start networkcommand including the specifier; the modem is configured to, based onreceiving the start network command including the specifier, check ifthe route selection policy includes a traffic descriptor associated withboth the first DNN and the second slice; the modem is configured to,based on the route selection policy including the second trafficdescriptor associated with both the first DNN and the second slice,establish a protocol data unit (PDU) session associated with the firstDNN and the second slice; the modem is configured to send to theoperating system an indication of the PDU session establishment; theoperating system, based on receiving the indication of the PDU sessionestablishment, is configured to set the interface status as up andassociated with the specifier; the operating system is configured tosend the identifier of the interface to the application; and theapplication is configured to utilize the interface for communication.

FIG. 13 illustrates a communications device 1300 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 10 . Thecommunications device 1300 includes a processing system 1302 coupled toa transceiver 1308 (e.g., a transmitter and/or a receiver). Thetransceiver 1308 is configured to transmit and receive signals for thecommunications device 1300 via an antenna 1310, such as the varioussignals as described herein. The processing system 1302 may beconfigured to perform processing functions for the communications device1300, including processing signals received and/or to be transmitted bythe communications device 1300.

The processing system 1302 includes a processor 1304 coupled to acomputer-readable medium/memory 1312 via a bus 1306. In certain aspects,the computer-readable medium/memory 1312 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1304, cause the processor 1304 to perform the operationsillustrated in FIG. 10 , or other operations for performing the varioustechniques discussed herein for supporting communication over multipleslices.

In certain aspects, computer-readable medium/memory 1312 stores code1328 for transmitting, from an OS to a modem, an indication of a startnetwork request originating from an application, the transmitting of theindication based on a determination that a traffic descriptor associatedwith the application is a non-default descriptor. In certain aspects,the code 1328 also provides for transmitting, to the application, anindication that the new network connection has been established based onthe one or more parameters. In certain aspects, the code 1328 alsoprovides for transmitting, to the modem, a command to establish the newnetwork connection, the command comprising the one or more parameters.

In certain aspects, computer-readable medium/memory 1312 stores code1330 for determining one or more parameters for establishing a newnetwork connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters. In certain aspects,code 1330 also provides for determining, by the OS, that the trafficdescriptor associated with the application is the non-defaultdescriptor, wherein the determination indicates that the application haspermission from the modem to communicate via the second network slice.

In certain aspects, computer-readable medium/memory 1312 stores code1332 for receiving, from the modem, an application descriptor listcomprising one or more traffic descriptors that are non-defaultdescriptors, the one or more traffic descriptors comprising anapplication identifier associated with the application, wherein anytraffic descriptor not on the application descriptor list is a defaultdescriptor. In certain aspects, code 1332 also provides for receiving,from the modem, the indication that the new network connection has beenestablished, wherein transmitting the indication to the application isin response to receiving the indication from the modem.

In certain aspects, computer-readable medium/memory 1312 stores code1334 for storing, by a modem, a route selection policy, the routeselection policy associating each of a plurality of traffic descriptorswith a corresponding data network name (DNN) and a corresponding slice,wherein a first traffic descriptor of the plurality of trafficdescriptors is associated with a first DNN and a first slice, wherein asecond traffic descriptor of the plurality of traffic descriptors isassociated with the first DNN and a second slice different than thefirst slice, wherein the first traffic descriptor is a defaultdescriptor for the first DNN.

In certain aspects, computer-readable medium/memory 1312 stores code1336 for executing an operating system and one or more applications.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1318 for storing a route selectionpolicy; and circuitry 1320 for executing an application.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1318 for transmitting, from an OSto a modem, an indication of a start network request originating from anapplication, the transmitting of the indication based on a determinationthat a traffic descriptor associated with the application is anon-default descriptor. In certain aspects, the circuitry 1318 alsoprovides for transmitting, to the application, an indication that thenew network connection has been established based on the one or moreparameters. In certain aspects, the circuitry 1318 also provides fortransmitting, to the modem, a command to establish the new networkconnection, the command comprising the one or more parameters.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1320 for establishing a newnetwork connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters. In certain aspects,circuitry 1320 also provides for determining, by the OS, that thetraffic descriptor associated with the application is the non-defaultdescriptor, wherein the determination indicates that the application haspermission from the modem to communicate via the second network slice.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1322 for receiving, from themodem, an application descriptor list comprising one or more trafficdescriptors that are non-default descriptors, the one or more trafficdescriptors comprising an application identifier associated with theapplication, wherein any traffic descriptor not on the applicationdescriptor list is a default descriptor. In certain aspects, circuitry1322 also provides for receiving, from the modem, the indication thatthe new network connection has been established, wherein transmittingthe indication to the application is in response to receiving theindication from the modem.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1324 for storing, by a modem, aroute selection policy, the route selection policy associating each of aplurality of traffic descriptors with a corresponding data network name(DNN) and a corresponding slice, wherein a first traffic descriptor ofthe plurality of traffic descriptors is associated with a first DNN anda first slice, wherein a second traffic descriptor of the plurality oftraffic descriptors is associated with the first DNN and a second slicedifferent than the first slice, wherein the first traffic descriptor isa default descriptor for the first DNN.

In certain aspects, the processor 1304 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1312.The processor 1304 includes circuitry 1326 for executing an operatingsystem and one or more applications.

FIG. 14 illustrates a communications device 1400 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 11 . Thecommunications device 1400 includes a processing system 1402 coupled toa transceiver 1408 (e.g., a transmitter and/or a receiver). Thetransceiver 1408 is configured to transmit and receive signals for thecommunications device 1400 via an antenna 1410, such as the varioussignals as described herein. The processing system 1402 may beconfigured to perform processing functions for the communications device1400, including processing signals received and/or to be transmitted bythe communications device 1400.

The processing system 1402 includes a processor 1404 coupled to acomputer-readable medium/memory 1412 via a bus 1406. In certain aspects,the computer-readable medium/memory 1412 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1404, cause the processor 1404 to perform the operationsillustrated in FIG. 11 , or other operations for performing the varioustechniques discussed herein for supporting communication over multipleslices.

In certain aspects, computer-readable medium/memory 1412 stores code1428 for transmitting, from an operating system (OS) to a modem, anindication of a request to establish a network connection originatingfrom an application, the request comprising a traffic descriptorassociated with the network connection, the traffic descriptor providedby the application. In certain aspects, the code 1428 also provides fortransmitting, to the application, an indication that the networkconnection is established.

In certain aspects, computer-readable medium/memory 1412 stores code1430 for receiving, from the modem, the indication that the networkconnection is established prior to transmitting the indication to theapplication, wherein the receiving the indication implicitly indicatesthat the modem approved the network connection.

In certain aspects, computer-readable medium/memory 1412 stores code1432 for approving, by the modem, the network connection based on arouting policy that provides mapping between the traffic descriptorprovided by the application and a data network name (DNN) or an accesspoint name (APN) associated with the traffic descriptor.

In certain aspects, computer-readable medium/memory 1412 stores code1434 for storing, by a modem, a route selection policy, the routeselection policy associating each of a plurality of traffic descriptorswith a corresponding data network name (DNN) and a corresponding slice,wherein a first traffic descriptor of the plurality of trafficdescriptors is associated with a first DNN and a first slice, wherein asecond traffic descriptor of the plurality of traffic descriptors isassociated with the first DNN and a second slice different than thefirst slice, wherein the first traffic descriptor is a defaultdescriptor for the first DNN.

In certain aspects, computer-readable medium/memory 1412 stores code1436 for executing an operating system and one or more applications.

In certain aspects, the processor 1404 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1412.The processor 1404 includes circuitry 1418 for transmitting, from anoperating system (OS) to a modem, an indication of a request toestablish a network connection originating from an application, therequest comprising a traffic descriptor associated with the networkconnection, the traffic descriptor provided by the application. Incertain aspects, the code 1428 also provides for transmitting, to theapplication, an indication that the network connection is established.

In certain aspects, the processor 1404 includes circuitry 1420 forreceiving, from the modem, the indication that the new networkconnection has been established, wherein transmitting the indication tothe application is in response to receiving the indication from themodem.

In certain aspects, the processor 1404 includes circuitry 1422 forapproving, by the modem, the network connection based on a routingpolicy that provides mapping between the traffic descriptor provided bythe application and a data network name (DNN) or an access point name(APN) associated with the traffic descriptor.

In certain aspects, the processor 1404 includes circuitry 1424 forstoring, by a modem, a route selection policy, the route selectionpolicy associating each of a plurality of traffic descriptors with acorresponding data network name (DNN) and a corresponding slice, whereina first traffic descriptor of the plurality of traffic descriptors isassociated with a first DNN and a first slice, wherein a second trafficdescriptor of the plurality of traffic descriptors is associated withthe first DNN and a second slice different than the first slice, whereinthe first traffic descriptor is a default descriptor for the first DNN.

In certain aspects, the processor 1404 includes circuitry 1426 forexecuting an operating system and one or more applications.

FIG. 15 illustrates a communications device 1500 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 12 . Thecommunications device 1500 includes a processing system 1502 coupled toa transceiver 1508 (e.g., a transmitter and/or a receiver). Thetransceiver 1508 is configured to transmit and receive signals for thecommunications device 1500 via an antenna 1510, such as the varioussignals as described herein. The processing system 1502 may beconfigured to perform processing functions for the communications device1500, including processing signals received and/or to be transmitted bythe communications device 1500.

The processing system 1502 includes a processor 1504 coupled to acomputer-readable medium/memory 1512 via a bus 1506. In certain aspects,the computer-readable medium/memory 1512 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1504, cause the processor 1504 to perform the operationsillustrated in FIG. 12 , or other operations for performing the varioustechniques discussed herein for supporting communication over multipleslices.

In certain aspects, computer-readable medium/memory 1512 stores code1528 for receiving, by the modem, from an operating system (OS), arequest for route identifier, the request for route identifiercomprising a traffic descriptor corresponding to a first applicationfrom which the request for route identifier originated. In certainaspects, the code 1528 also provides for receiving, by the modem, astart network request comprising the route identifier. In certainaspects, the code 1528 also provides for receiving, by the OS, the startnetwork request from the first application.

In certain aspects, computer-readable medium/memory 1512 stores code1530 for transmitting a route identifier to the OS, the route identifiergenerated by a modem based on a routing policy that provides mappingbetween the traffic descriptor and a network route.

In certain aspects, computer-readable medium/memory 1512 stores code1532 for establishing, in response to the start network request, anetwork connection via the network route. Code 1532 also provides forestablishing a protocol data unit (PDU) session associated with thefirst DNN via the first network slice.

In certain aspects, computer-readable medium/memory 1512 stores code1534 for storing, by a modem, a route selection policy, the routeselection policy associating each of a plurality of traffic descriptorswith a corresponding data network name (DNN) and a corresponding slice,wherein a first traffic descriptor of the plurality of trafficdescriptors is associated with a first DNN and a first slice, wherein asecond traffic descriptor of the plurality of traffic descriptors isassociated with the first DNN and a second slice different than thefirst slice, wherein the first traffic descriptor is a defaultdescriptor for the first DNN.

In certain aspects, computer-readable medium/memory 1512 stores code1536 for executing an operating system and one or more applications.

In certain aspects, the processor 1504 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1512.The processor 1504 includes circuitry 1518 for receiving, by the modem,from an operating system (OS), a request for route identifier, therequest for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated. In certain aspects, the circuitry 1518 alsoprovides for receiving, by the modem, a start network request comprisingthe route identifier. In certain aspects, the circuitry 1518 alsoprovides for receiving, by the OS, the start network request from thefirst application.

In certain aspects, the processor 1504 includes circuitry 1520 fortransmitting a route identifier to the OS, the route identifiergenerated by a modem based on a routing policy that provides mappingbetween the traffic descriptor and a network route.

In certain aspects, the processor 1504 includes circuitry 1522 forapproving, by the modem, the network connection based on a routingpolicy that provides mapping between the traffic descriptor provided bythe application and a data network name (DNN) or an access point name(APN) associated with the traffic descriptor.

In certain aspects, the processor 1504 includes circuitry 1524 forstoring, by a modem, a route selection policy, the route selectionpolicy associating each of a plurality of traffic descriptors with acorresponding data network name (DNN) and a corresponding slice, whereina first traffic descriptor of the plurality of traffic descriptors isassociated with a first DNN and a first slice, wherein a second trafficdescriptor of the plurality of traffic descriptors is associated withthe first DNN and a second slice different than the first slice, whereinthe first traffic descriptor is a default descriptor for the first DNN.

In certain aspects, the processor 1504 includes circuitry 1526 forexecuting an operating system and one or more applications.

Example Aspects

Implementation examples are described in the following numbered clauses:

1. A method for wireless communication at a user equipment (UE),comprising: transmitting, from an operating system (OS) to a modem, anindication of a start network request originating from an application,the transmitting of the indication based on a determination that atraffic descriptor associated with the application is a non-defaultdescriptor; determining one or more parameters for establishing a newnetwork connection for the application, the one or more parametersdetermined based on a routing policy that provides mapping between thetraffic descriptor and the one or more parameters; and transmitting, tothe application, an indication that the new network connection has beenestablished based on the one or more parameters.

2. The method of aspect 1, further comprising receiving, from the modem,an application descriptor list comprising one or more trafficdescriptors that are non-default descriptors, the one or more trafficdescriptors comprising an application identifier associated with theapplication, wherein any traffic descriptor not on the applicationdescriptor list is a default descriptor.

3. The method of any of aspects 1 and 2, wherein the default descriptoris associated with a first DNN and a first network slice, wherein thenon-default descriptor is associated with the first DNN and a secondnetwork slice, and wherein the default descriptor is a defaultdescriptor for the first DNN.

4. The method of any of aspects 1-3, wherein the non-default descriptorindicates that the application communicates via the second networkslice.

5. The method of any of aspects 1-4, further comprising determining, bythe OS, that the traffic descriptor associated with the application isthe non-default descriptor, wherein the determination indicates that theapplication has permission from the modem to communicate via the secondnetwork slice.

6. The method of any of aspects 1-5, wherein the one or more parameterscomprise one or more of a data network name (DNN) or a network slice,wherein each of the DNN and the network slice are associated with thetraffic descriptor.

7. The method of any of aspects 1-6, further comprising transmitting, tothe modem, a command to establish the new network connection, thecommand comprising the one or more parameters.

8. The method of any of aspects 1-7, further comprising receiving, fromthe modem, the indication that the new network connection has beenestablished, wherein transmitting the indication to the application isin response to receiving the indication from the modem.

9. A method for wireless communication at a user equipment (UE),comprising: transmitting, from an operating system (OS) to a modem, anindication of a request to establish a network connection originatingfrom an application, the request comprising a traffic descriptorassociated with the network connection, the traffic descriptor providedby the application; and transmitting, to the application, an indicationthat the network connection is established.

10. The method of aspect 9, wherein the traffic descriptor is indicativeof one or more of a service requested for the network connection and anetwork slice associated with the network connection.

11. The method of any of aspect 9 and 10, further comprising determiningwhether the traffic descriptor exists in a database maintained by theOS, wherein if the traffic descriptor exists in the database, the methodfurther comprises transmitting, to the modem, one or more of a datanetwork name (DNN) or an access point name (APN) associated with thetraffic descriptor in the database, and wherein if the trafficdescriptor does not exist in the database, the method further comprisestransmitting, to the modem, the traffic descriptor.

12. The method of any of aspects 9-11, wherein the traffic descriptorcomprises one or more of a data network name (DNN) or an access pointname (APN) associated with the network connection.

13. The method of any of aspects 9-12, further comprising receiving,from the modem, the indication that the network connection isestablished prior to transmitting the indication to the application,wherein the receiving the indication implicitly indicates that the modemapproved the network connection.

14. The method of any of aspects 9-13, further comprising approving, bythe modem, the network connection based on a routing policy thatprovides mapping between the traffic descriptor provided by theapplication and a data network name (DNN) or an access point name (APN)associated with the traffic descriptor.

15. A method for wireless communication at a user equipment (UE),comprising: receiving, by the modem, from an operating system (OS), arequest for route identifier, the request for route identifiercomprising a traffic descriptor corresponding to a first applicationfrom which the request for route identifier originated; transmitting aroute identifier to the OS, the route identifier generated by a modembased on a routing policy that provides mapping between the trafficdescriptor and a network route; receiving, by the modem, a start networkrequest comprising the route identifier; and establishing, in responseto the start network request, a network connection via the networkroute.

16. The method of aspect 15, wherein the routing policy provides mappingbetween each of a plurality of traffic descriptors and a correspondingnetwork route, and wherein each corresponding network route comprises adata network name (DNN) and an indication of a network slice.

17. The method of any of aspects 15 and 16, wherein a first trafficdescriptor of the plurality of traffic descriptors is associated with afirst DNN and a first network slice, wherein a second traffic descriptorof the plurality of traffic descriptors is associated with the first DNNand a second network slice, and wherein the first traffic descriptor isa default descriptor for the first DNN.

18. The method of any of aspects 15-17, wherein the transmitting theroute identifier to the OS indicates that the first application haspermission from the modem to communicate via the second network slice.

19. The method of any of aspects 15-18, wherein establishing the networkconnection further comprises: determining, by the modem, a first datanetwork name and a first network slice associated with the routeidentifier; and establishing a protocol data unit (PDU) sessionassociated with the first DNN via the first network slice.

20. The method of any of aspects 15-19, further comprising storing anindex mapping the network route to the generated route identifier,wherein the route identifier is a random string of one or more values.

21. The method of any of aspects 15-20, wherein the traffic descriptoris added to the request for route identifier by the OS.

22. The method of any of aspects 15-21, wherein the start networkrequest originates from the first application, the method furthercomprising: receiving, by the OS, the start network request from thefirst application; in response to receiving the start network request,determining whether an existing network connection corresponding to theroute identifier is available; when the existing network connection isavailable, enabling, by the OS, the first application for communicationover the existing network connection; and when the existing networkconnection is not available, transmitting the start network request tothe modem.

23. The method of any of aspects 15-22, further comprising notifying theOS, by the modem, that the network connection has been established.

24. A user equipment (UE), comprising: a memory; a modem; and aprocessor coupled to the memory and the modem, the memory and theprocessor being configured to: transmit, from an operating system (OS)executing on the processor to the modem, an indication of a startnetwork request originating from an application executing on the OS, theindication being transmitted based on a determination that a trafficdescriptor associated with the application is a non-default descriptor;determine one or more parameters for establishing a new networkconnection for the application, the one or more parameters determinedbased on a routing policy that provides mapping between the trafficdescriptor and the one or more parameters; and transmit, to theapplication, an indication that the new network connection has beenestablished based on the one or more parameters.

25. The UE of aspect 24, wherein the memory and the processor arefurther configured to receive, from the modem, an application descriptorlist comprising one or more traffic descriptors that are non-defaultdescriptors, the one or more traffic descriptors comprising anapplication identifier associated with the application, wherein anytraffic descriptor not on the application descriptor list is a defaultdescriptor.

26. The UE of any of aspects 24 and 25, wherein the default descriptoris associated with a first DNN and a first network slice, wherein thenon-default descriptor is associated with the first DNN and a secondnetwork slice, and wherein the default descriptor is a defaultdescriptor for the first DNN.

27. The UE of any of aspects 24-26, and wherein the non-defaultdescriptor indicates that the application communicates via the secondnetwork slice.

28. The UE of any of aspects 24-27, wherein the one or more parameterscomprise one or more of a data network name (DNN) or a network slice,wherein each of the DNN and the network slice are associated with thetraffic descriptor.

29. The UE of any of aspects 24-28, wherein the memory and the processorare further configured to transmit, to the modem, a command to establishthe new network connection, the command comprising the one or moreparameters.

30. The UE of any of aspects 24-29, wherein the memory and the processorare further configured to receive, from the modem, the indication thatthe new network connection has been established, wherein the memory andthe processor, being configured to transmit the indication to theapplication, are further configured to transmit the indication to theapplication in response to receiving the indication from the modem.

31. An apparatus comprising means for performing the method of any ofaspects 1 through 23.

32. An apparatus comprising at least one processor and a memory coupledto the at least one processor, the memory comprising code executable bythe at least one processor to cause the apparatus to perform the methodof any of aspects 1 through 23.

33. A computer readable medium storing computer executable code thereonfor wireless communications that, when executed by at least oneprocessor, cause an apparatus to perform the method of any of aspects 1through 23.

Additional Considerations

The techniques described herein may be used for various wirelesscommunication technologies, such as NR (e.g., 5G NR), 3GPP Long TermEvolution (LTE), LTE-Advanced (LTE-A), code division multiple access(CDMA), time division multiple access (TDMA), frequency divisionmultiple access (FDMA), orthogonal frequency division multiple access(OFDMA), single-carrier frequency division multiple access (SC-FDMA),time division synchronous code division multiple access (TD-SCDMA), andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. CDMA2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as NR (e.g. 5GRA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS). LTEand LTE-A are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE,LTE-A and GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). CDMA2000 and UMB are describedin documents from an organization named “3rd Generation PartnershipProject 2” (3GPP2). NR is an emerging wireless communications technologyunder development.

In 3GPP, the term “cell” can refer to a coverage area of a Node B (NB)and/or a NB subsystem serving this coverage area, depending on thecontext in which the term is used. In NR systems, the term “cell” andBS, next generation NodeB (gNB or gNodeB), access point (AP),distributed unit (DU), carrier, or transmission reception point (TRP)may be used interchangeably. A BS may provide communication coverage fora macro cell, a pico cell, a femto cell, and/or other types of cells. Amacro cell may cover a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs withservice subscription. A pico cell may cover a relatively smallgeographic area and may allow unrestricted access by UEs with servicesubscription. A femto cell may cover a relatively small geographic area(e.g., a home) and may allow restricted access by UEs having anassociation with the femto cell (e.g., UEs in a Closed Subscriber Group(CSG), UEs for users in the home, etc.). A BS for a macro cell may bereferred to as a macro BS. A BS for a pico cell may be referred to as apico BS. ABS for a femto cell may be referred to as a femto BS or a homeBS.

A UE may also be referred to as a mobile station, a terminal, an accessterminal, a subscriber unit, a station, a Customer Premises Equipment(CPE), a cellular phone, a smart phone, a personal digital assistant(PDA), a wireless modem, a wireless communication device, a handhelddevice, a laptop computer, a cordless phone, a wireless local loop (WLL)station, a tablet computer, a camera, a gaming device, a netbook, asmartbook, an ultrabook, an appliance, a medical device or medicalequipment, a biometric sensor/device, a wearable device such as a smartwatch, smart clothing, smart glasses, a smart wrist band, smart jewelry(e.g., a smart ring, a smart bracelet, etc.), an entertainment device(e.g., a music device, a video device, a satellite radio, etc.), avehicular component or sensor, a smart meter/sensor, industrialmanufacturing equipment, a global positioning system device, or anyother suitable device that is configured to communicate via a wirelessor wired medium. Some UEs may be considered machine-type communication(MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include,for example, robots, drones, remote devices, sensors, meters, monitors,location tags, etc., that may communicate with a BS, another device(e.g., remote device), or some other entity. A wireless node mayprovide, for example, connectivity for or to a network (e.g., a widearea network such as Internet or a cellular network) via a wired orwireless communication link. Some UEs may be consideredInternet-of-Things (IoT) devices, which may be narrowband IoT (NB-IoT)devices.

In some examples, access to the air interface may be scheduled. Ascheduling entity (e.g., a BS) allocates resources for communicationamong some or all devices and equipment within its service area or cell.The scheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more subordinateentities. That is, for scheduled communication, subordinate entitiesutilize resources allocated by the scheduling entity. Base stations arenot the only entities that may function as a scheduling entity. In someexamples, a UE may function as a scheduling entity and may scheduleresources for one or more subordinate entities (e.g., one or more otherUEs), and the other UEs may utilize the resources scheduled by the UEfor wireless communication. In some examples, a UE may function as ascheduling entity in a peer-to-peer (P2P) network, and/or in a meshnetwork. In a mesh network example, UEs may communicate directly withone another in addition to communicating with a scheduling entity.

The methods disclosed herein comprise one or more steps or actions forachieving the methods. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language of the claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112(f) unless the element is expressly recited using the phrase“means for” or, in the case of a method claim, the element is recitedusing the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the physical (PHY) layer. In the case ofa user terminal (see FIG. 1 , e.g., “user equipment (UE)”), a userinterface (e.g., keypad, display, mouse, joystick, etc.) may also beconnected to the bus. The bus may also link various other circuits suchas timing sources, peripherals, voltage regulators, power managementcircuits, and the like, which are well known in the art, and therefore,will not be described any further. The processor may be implemented withone or more general-purpose and/or special-purpose processors. Examplesinclude microprocessors, microcontrollers, DSP processors, and othercircuitry that can execute software. Those skilled in the art willrecognize how best to implement the described functionality for theprocessing system depending on the particular application and theoverall design constraints imposed on the overall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein, for example, instructions for performing the operationsdescribed herein and illustrated in FIGS. 10-12 .

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

The invention claimed is:
 1. A method for wireless communication at auser equipment (UE), comprising: receiving, by a modem, from anoperating system (OS), a request for route identifier, the request forroute identifier comprising a traffic descriptor corresponding to afirst application from which the request for route identifieroriginated; transmitting a route identifier to the OS, the routeidentifier generated by the modem based on a routing policy thatprovides mapping between the traffic descriptor and a network route,wherein the routing policy provides mapping between each of a pluralityof traffic descriptors and a corresponding network route, and whereineach corresponding network route comprises a data network name (DNN) andan indication of a network slice; receiving, by the modem, a startnetwork request comprising the route identifier; and establishing, inresponse to the start network request, a network connection via thenetwork route.
 2. The method of claim 1, wherein a first trafficdescriptor of the plurality of traffic descriptors is associated with afirst DNN and a first network slice, wherein a second traffic descriptorof the plurality of traffic descriptors is associated with the first DNNand a second network slice, and wherein the first traffic descriptor isa default descriptor for the first DNN.
 3. The method of claim 2,wherein the transmitting the route identifier to the OS indicates thatthe first application has permission from the modem to communicate viathe second network slice.
 4. The method of claim 1, wherein establishingthe network connection further comprises: determining, by the modem, afirst data network name and a first network slice associated with theroute identifier; and establishing a protocol data unit (PDU) sessionassociated with the first DNN via the first network slice.
 5. The methodof claim 1, further comprising storing an index mapping the networkroute to the route identifier, wherein the route identifier is a randomstring of one or more values.
 6. The method of claim 1, wherein thetraffic descriptor is added to the request for route identifier by theOS.
 7. The method of claim 1, wherein the start network requestoriginates from the first application, the method further comprising:receiving, by the OS, the start network request from the firstapplication; in response to receiving the start network request,determining whether an existing network connection corresponding to theroute identifier is available; when the existing network connection isavailable, enabling, by the OS, the first application for communicationover the existing network connection; and when the existing networkconnection is not available, transmitting the start network request tothe modem.
 8. The method of claim 1, further comprising notifying theOS, by the modem, that the network connection has been established.
 9. Auser equipment (UE), comprising: a memory; a modem; and a processorcoupled to the memory and the modem, the memory and the processor beingconfigured to: receive, via a modem, from an operating system (OS), arequest for route identifier, the request for route identifiercomprising a traffic descriptor corresponding to a first applicationfrom which the request for route identifier originated; transmit a routeidentifier to the OS, the route identifier generated by the modem basedon a routing policy that provides mapping between the traffic descriptorand a network route, wherein the routing policy provides mapping betweeneach of a plurality of traffic descriptors and a corresponding networkroute, and wherein each corresponding network route comprises a datanetwork name (DNN) and an indication of a network slice; receive, viathe modem, a start network request comprising the route identifier; andestablish, in response to the start network request, a networkconnection via the network route.
 10. The UE of claim 9, wherein a firsttraffic descriptor of the plurality of traffic descriptors is associatedwith a first DNN and a first network slice, wherein a second trafficdescriptor of the plurality of traffic descriptors is associated withthe first DNN and a second network slice, and wherein the first trafficdescriptor is a default descriptor for the first DNN.
 11. The UE ofclaim 10, wherein the memory and the processor are further configured totransmit the route identifier to the OS indicates that the firstapplication has permission from the modem to communicate via the secondnetwork slice.
 12. The UE of claim 9, wherein the memory and theprocessor configured to establish the network connection is furtherconfigured to: determine, by the modem, a first data network name and afirst network slice associated with the route identifier; and establisha protocol data unit (PDU) session associated with the first DNN via thefirst network slice.
 13. The UE of claim 9, wherein the memory and theprocessor are further configured to store an index mapping the networkroute to the route identifier, wherein the route identifier is a randomstring of one or more values.
 14. The UE of claim 9, wherein the trafficdescriptor is added to the request for route identifier by the OS. 15.The UE of claim 9, wherein the start network request originates from thefirst application, and the memory and the processor are furtherconfigured to: receive, via the OS, the start network request from thefirst application; in response to receiving the start network request,determine whether an existing network connection corresponding to theroute identifier is available; when the existing network connection isavailable, enable, via the OS, the first application for communicationover the existing network connection; and when the existing networkconnection is not available, transmit the start network request to themodem.
 16. The UE of claim 9, wherein the memory and the processor arefurther configured to notify the OS, via the modem, that the networkconnection has been established.
 17. A non-transitory computer-readablestorage medium that stores instructions that, when executed by aprocessor of a user equipment (UE), cause the UE to perform a method ofwireless communication, the method comprising: receiving, by a modem,from an operating system (OS), a request for route identifier, therequest for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated; transmitting a route identifier to the OS, theroute identifier generated by the modem based on a routing policy thatprovides mapping between the traffic descriptor and a network route,wherein the routing policy provides mapping between each of a pluralityof traffic descriptors and a corresponding network route, and whereineach corresponding network route comprises a data network name (DNN) andan indication of a network slice; receiving, by the modem, a startnetwork request comprising the route identifier; and establishing, inresponse to the start network request, a network connection via thenetwork route.
 18. A method for wireless communication at a userequipment (UE), comprising: receiving, by a modem, from an operatingsystem (OS), a request for route identifier, the request for routeidentifier comprising a traffic descriptor corresponding to a firstapplication from which the request for route identifier originated;transmitting a route identifier to the OS, the route identifiergenerated by the modem based on a routing policy that provides mappingbetween the traffic descriptor and a network route; receiving, by themodem, a start network request comprising the route identifier; andestablishing, in response to the start network request, a networkconnection via the network route, wherein establishing the networkconnection comprises: determining, by the modem, a first data networkname and a first network slice associated with the route identifier; andestablishing a protocol data unit (PDU) session associated with thefirst DNN via the first network slice.
 19. A user equipment (UE),comprising: a memory; a modem; and a processor coupled to the memory andthe modem, the memory and the processor being configured to: receive,via a modem, from an operating system (OS), a request for routeidentifier, the request for route identifier comprising a trafficdescriptor corresponding to a first application from which the requestfor route identifier originated; transmit a route identifier to the OS,the route identifier generated by the modem based on a routing policythat provides mapping between the traffic descriptor and a networkroute; receive, via the modem, a start network request comprising theroute identifier; and establish, in response to the start networkrequest, a network connection via the network route, wherein the memoryand the processor configured to establish the network connection isfurther configured to: determine, by the modem, a first data networkname and a first network slice associated with the route identifier; andestablish a protocol data unit (PDU) session associated with the firstDNN via the first network slice.
 20. A non-transitory computer-readablestorage medium that stores instructions that, when executed by aprocessor of a user equipment (UE), cause the UE to perform a method ofwireless communication, the method comprising: receiving, by a modem,from an operating system (OS), a request for route identifier, therequest for route identifier comprising a traffic descriptorcorresponding to a first application from which the request for routeidentifier originated; transmitting a route identifier to the OS, theroute identifier generated by the modem based on a routing policy thatprovides mapping between the traffic descriptor and a network route;receiving, by the modem, a start network request comprising the routeidentifier; and establishing, in response to the start network request,a network connection via the network route, wherein establishing thenetwork connection comprises: determining, by the modem, a first datanetwork name and a first network slice associated with the routeidentifier; and establishing a protocol data unit (PDU) sessionassociated with the first DNN via the first network slice.